Detecting correlation from data

ABSTRACT

A system and a priori method of discovering dependencies between relational database column pairs and application of discoveries to query optimization is provided. For each candidate column pair remaining after simultaneously generating column pairs, pruning pairs not satisfying specified heuristic constraints, and eliminating pairs with trivial instances of correlation, a random sample of data values is collected. A candidate column pair is tested for the existence of a soft functional dependency (FD), and if a dependency is not found, statistically tested for correlation using a robust chi-squared statistic. Column pairs for which either a soft FD or a statistical correlation exists are prioritized for recommendation to a query optimizer, based on any of: strength of dependency, degree of correlation, or adjustment factor; statistics for recommended columns pairs are tracked to improve selectivity estimates. Additionally, a dependency graph representing correlations and dependencies as edges and column pairs as nodes is provided.

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention relates generally to the field of relational database query optimization. More specifically, the present invention is related to correlation detection and dependency discovery between columns in a relational database.

2. Discussion of Prior Art

Dependencies between columns in relational databases can be exploited to optimize queries, but can also result in inaccurate estimates produced by query optimizers. Because query optimizers usually assume that columns are statistically independent, unaccounted for dependencies can lead to selectivity underestimation of conjunctive predicates by several orders of magnitude. Often-times a query optimizer in a relational database chooses a sub-optimal plan because of the inaccurate assumption of independence between two or more columns. Such an assumption is often made by query optimizers known in the art because it simplifies estimation; for example, the selectivity of conjunctive predicates based on two columns can be estimated by simply multiplying the individual selectivity of a column with the other.

Addressing these issues of relaxing statistical independence assumptions in selectivity estimations are query-driven and data-driven approaches. Query-driven approaches focus on information contained in a query workload, whereas data-driven methods analyze data values to discover correlations, or general statistical dependencies, between relational database columns. By stating the existence of a soft functional dependency (FD) between columns C₁ and C₂, a generalization of the classical notion of a hard FD in which a value in C₁ completely determines a corresponding value in C₂ is implied. A soft FD, denoted by C₁

C₂, indicates that a value of C₁ determines a corresponding value in C₂ not with certainty, but with high probability. An example of a hard FD is given by “Country” and “Continent”; the former completely determines the latter. On the other hand, a soft FD between the make and model of a car is shown in the following example; given that “Model=323”, “Make=Mazda” with high probability and “Make=BMW” with small probability. Two types of trivial cases are also identified; a soft key having a small number of distinct values in a given column and a trivial column having either only null values or only a single distinct value in a given column. The values in any row of a trivial column are trivially determined by values in any other column, which leads to spurious correlations.

In non-patent literature “Exploiting Statistics on Query Expressions for Optimization”, Bruno and Chaudhuri disclose the use query workload (i.e. a list of relevant queries) together with optimizer estimates of query execution times for determining a beneficial set of Statistics of Intermediate Tables (SITS) to retain. SITS are statistics on query expressions that can be used to avoid large selectivity estimation errors due to independence assumptions.

Alternatively, a query feedback system (QFS) uses feedback from query execution to increase optimizer accuracy. In “LEO-DB2™'s learning optimizer” by Markl et al., DB2™ learning optimizer (LEO) is presented as a typical example of a QFS. LEO compares the actual selectivities of query results with a query optimizer's estimated selectivities. In this way, LEO can detect errors caused by faulty independence assumptions and create adjustment factors which can be applied in the future to improve the optimizer's selectivity estimates.

The self-adaptive histogram set (SASH) algorithm, disclosed in “A self-adaptive histogram set for dynamically changing workloads” by Lim et al., discloses another query-driven approach by creating clusters of disjoint columns in a relational database. Clustered columns are treated as being correlated whereas columns in different clusters are considered independent. In other words, SASH approximates the full joint distribution of the columns by maintaining detailed histograms on certain low-dimensional marginals in accordance with a high-level statistical interaction model. Joint frequencies are then computed as a product of marginals. Maintaining detailed histograms together with a high-level statistical interaction model can be very expensive, which limits the applicability of the SASH algorithm in commercial systems. As with other query feedback systems such as LEO, less optimal query plans can be chosen if the system has not yet received enough feedback, either during the initial startup period or after a sudden change in query workload. During one of these slow learning phases, a query optimizer is likely to avoid query plans with accurate feedback-based cost estimates in favor of other plans that appear to be less expensive, due to cost estimates based on limited quantities of actual data and faulty independence assumptions.

Most data-driven methods use discovered correlations to construct and maintain a synopsis (lossy compressed representation) of the joint distribution of numerical attributes. Getoor, et al., for example, use probabilistic relational models extending Bayesian network models to the relational setting for selectivity estimation in “Selectivity estimation using probabilistic models”. Deshpande, et al. provide a technique in “Independence is Good: Dependency-based histogram synopses for high-dimensional data” which, similarly to SASH, combines a Markov network model with a set of low-dimensional histograms. However, synopses are constructed based on a full scan of the base data rather from query feedback. Both of the foregoing techniques search through the space of possible models and evaluate them according to a scoring function. As with SASH, the high cost of these methods severely limits their practical applicability.

The method of Cheng et al. provided in “Learning belief networks from data: An Information theory based approach” typifies a slightly different approach to constructing a synopsis (specifically, a Bayesian network model) from the base data. Instead of searching through a space of possible models, the method assesses the dependency between pairs of columns by using conditional independence tests based on a “mutual information” measure. The method requires that all attributes be discrete and that there be no missing data values. The method is also not scalable as it requires processing of the entire dataset.

Mining association rules and semantic integrity constraints are approaches limited in that dependencies involve relationships between a few specific values of a pair of attributes, rather than an overall relationship between attributes themselves. For example, an association might assert that ten percent of married people between ages fifty and sixty have at least two cars. This rule concerns specific values of marital status, age, and number of cars attributes.

To account for statistical interdependence between columns of in a relational database, the “bump-hunting” system (B-HUNT) disclosed by Haas et al. in “BHUNT: Automatic discovery of fuzzy algebraic constraints in relational data” searches for column pairs that might have interesting and useful correlations by systematically enumerating candidate pairs and simultaneously pruning candidates that do not appear promising by using a flexible set of heuristics. B-HUNT also analyzes a sample of rows in order to ensure scalability to larger relational databases. B-HUNT uses bump hunting techniques to discover soft algebraic relationships between columns having numerical attributes. General correlations between categorical values are not considered.

The non-patent literature by Brin, Motwani, and Silverstein, “Beyond Market Baskets: Generalizing Association Rules to Correlations” discloses the determination of “correlation rules” in a market-basket context. Brin et al. propose the use of chi-square tests to check for independence; the use of chi-square tests for testing independence is well-known in the art. Brin et al. do not disclose a setting that is for general numeric data and several types of general statistical dependencies, not a specialized type of dependency based on “market-basket” input transaction records. Brin et al. does not address sequential testing for different kinds of dependencies, arranging data in buckets such that the chi-square contingency table has an appropriate, data-dependent number of rows and columns, using data sampling to make algorithm scalable, systematically choosing likely pairs for analysis by combining exhaustive enumeration with heuristic pruning, and ranking the detected correlated column pairs, so that highest ranked pairs are first recommended to the query optimizer

U.S. Pat. No. 5,899,986 requires a workload to determine what set of statistics to create, and relies on information in the system catalog to determine what column groups to generate statistics on, as opposed to a sample. The patent is limited in that it does not provide for a determination of relationships between tables, and is not enabled to discover general correlations through a chi-square test, nor does it rank discovered correlations. Function dependence detection in the disclosed invention is based on information from a systems catalog, not on information based on a sample.

Prior art is limited in that there is no premise for determining correlations between general categorical attributes, nor is there a robust method for determining numerical correlations. Additionally, prior approaches are limited in their provision of correlation and dependency information to a query optimizer, a priori. By contrast, the present invention provides for prioritization of a priori column pair and statistic recommendations to a query optimizer with respect to any of: a degree of correlation, strength of dependency, or adjustment factor.

Whatever the precise merits, features, and advantages of the above cited references, none of them achieves or fulfills the purposes of the present invention.

SUMMARY OF THE INVENTION

The system and method of the present invention discover statistical correlations and identify soft functional dependencies between column pair attributes, in a single relational database and across multiple relational databases. Database system catalog statistics and a random sample are utilized to detect the existence of soft functional dependencies and to test for the existence of correlations between either numerical attributes or categorical attributes for columns in a pair. Also provided is a dependency graph representation comprised of node pairs representing discovered column pairs and proportionately weighted edges representing the strength of functional dependencies and correlations between columns in a pair.

Prior to correlation detection analyses, candidate column pairs representing potentially correlated attributes and values are generated. A set of heuristic pruning rules specifying constraints are simultaneously applied to limit the number of column pairs generated. Pruning rules are comprised of constraints based on allowable data types, statistical properties of columns, schema information, and workload information. For each candidate column pair that has not been pruned, actual dependencies, if any, are determined during subsequent correlation detection analysis by utilizing system catalog statistics and, if needed, a random sample of values selected from column pairs.

In an initial step of correlation detection, given a candidate column pair as input, system catalog statistics are analyzed to determine whether correlation between columns is spurious. Using a specific system catalog statistic, the number of distinct values in a given column, it is determined whether one or both columns in a candidate column pair is “trivial” in that it is either single-valued or a soft key. If it is determined as such, then the candidate column pair is discarded.

If an input column pair is not discarded, then in a subsequent step, a random sample of value pairs is selected and sampled data is used to test the input column pair for the existence of a soft functional dependency. The existence of a soft FD is asserted if the value in one column implies with high probability the corresponding value in the other column, and is determined by a ratio of the number of distinct values in the two input columns, as determined from sampled data.

If a functional dependency is not detected during the second step of correlation detection, value pairs from a random sample are analyzed for the presence of correlation by using a robust, statistical chi-squared test. Prior to statistical testing, values in each column are categorized and a contingency table is created to carry out a chi-squared test. Candidate columns are declared correlated if either: the number of zeros in an associated contingency table is greater than a specified number; or if both the number of zeros in an associated contingency table is less than a specified number and a corresponding chi-squared statistic for an associated contingency table exceeds a specified value. The degree of correlation between columns in a pair is given by either the p-value of a corresponding chi-squared test or by the value of a mean-square contingency.

Column pairs within which soft functional dependencies and correlations are found are prioritized in order of optimization potential, from which a selected set is provided to a query optimizer. Thus, a query optimizer is enabled to track statistics on column pairs having the greatest potential for impact in query optimization. For each selected pair (C₁, C₂), a query optimizer collects a column group statistic, denoted by |C₁, C₂|, which is the number of distinct combinations of values in each column. Using a column group statistic allows a query optimizer to produce an improved selectivity estimate, S′_(p) ₁ _({circumflex over ( )}p) ₂ =1/|C₁, C₂|, for the execution of a query plan.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 a illustrates a general system diagram of the present invention.

FIG. 1 b illustrates a general process flow for the method of the present invention.

FIG. 2 is a correlation detection algorithm of the present invention.

FIG. 3 illustrates a dependency graph representing correlations detected between column pairs in a relational database.

FIG. 4 illustrates an exemplary correlated column pair.

FIG. 5 is a column group statistic recommendation algorithm for a query optimizer.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

While this invention is illustrated and described in a preferred embodiment, the invention may be produced in many different configurations. There is depicted in the drawings, and will herein be described in detail, a preferred embodiment of the invention, with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention and the associated functional specifications for its construction and is not intended to limit the invention to the embodiment illustrated. Those skilled in the art will envision many other possible variations within the scope of the present invention.

Referring now to FIG. 1 a, a general system diagram of the present invention (hereafter, CORDS) is shown. A database utility, DB2 RUNSTATS 100, collects statistics on data in a relational database and records them in an associated system catalog 102. Relational data 104 is sampled; data is analyzed to determine dependencies and correlations 106; and in one embodiment, dependencies and correlations are displayed in dependency graph 108. Column group statistics for column pairs between which dependencies and correlations are displayed are also recommended and a profile is made. Column group statistics are then recommended 110 to DB2 RUNSTATS 100 utility. The next time DB2 RUNSTATS 100 collects statistics, it collects the recommended column group statistics. Query optimizer 112 obtains column group statistics from system catalog 102, and computes adjustments to a query execution plan (QEP). After estimating cardinalities and total cost for an adjusted query plan, query optimizer outputs an optimal, least-cost QEP.

Generation of Candidate Pairs

Shown in FIG. 1 b is a general process flow diagram for CORDS and associated preliminary phases. Beginning with a preliminary phase, candidate pairs of columns are generated for subsequent correlation testing. A candidate is defined as a triple (a₁, a₂, P), where a_(i) (i=1, 2) is an attribute of the form R.c (e.g., EMPLOYEES.ID, ACCOUNTS.Balance). A pairing rule, P, specifies how each attribute value in column a₁ is paired with an attribute value in column a₂ in order to form a set of potentially dependent or correlated attribute-value pairs. When both attribute columns lie in the same table, R, and each a₁ value is paired with an a₂ value in the same row, pairing rule P is trivial and is denoted by the symbol, ∅_(R). A nontrivial pairing rule describes the manner in which a table is joined with itself, if each a₁ value is paired with an a₂ value not in the same row. When attribute columns a₁ and a₂ lie in different tables that are joined during query processing; pairing rule P is specified as a two-table join predicate.

Candidates column pairs are generated by first discovering pairing rules and then, for each pairing rule, enumerating all column pairs specified by this pairing rule. Each discovered non-trivial pairing rule, P, connects a pair of tables R and S, and generates candidate column pairs of the form (R.a, S.b, P). Each discovered trivial pairing rule refers to a table R, and generates candidate column pairs of the form (R.a, R.b, ∅_(R))

In one embodiment, nontrivial pairing rules discovered are those that appear to be primary-key-to-foreign-key join predicates, since such join predicates are likely to occur in query workloads. To find such nontrivial pairing rules, a set K comprised of columns declared as either primary or unique keys is identified, along with each column a not declared a key, for which the following inequality is satisfied: $\begin{matrix} {\frac{\#\quad{{distinctValues}(a)}}{\#\quad{{rows}(a)}} \geq {1 - ɛ}} & (1) \end{matrix}$ where ε is a user or system-specified tolerance. For each column a in set K, every other column in a relational database is examined to find potential foreign-key columns to complete a pairing rule. A column b is considered a foreign-key match for column a if either column a is a declared primary key and column b is a declared foreign key for the primary key, or if every attribute value in a sample from column b has a matching attribute value in column a.

In tandem with the generation of candidate pairs, a flexible set of heuristic pruning rules are applied to limit the total number of candidate pairs that are subsequently analyzed. Pruning rules are comprised of: type constraints in which candidate columns whose data type does not belong to a specified set are pruned (i.e., columns with non-integer data, columns with strings of less than ten characters); statistical constraints in which tables and columns that do not have specified statistical properties are pruned (i.e., columns with few distinct values or tables with few rows); pairing constraints in which candidates whose pairing rules fail to meet specified criteria are pruned (i.e., pairing rules that correspond to explicitly declared primary-key-to-foreign-key relationships); and workload constraints in which candidate columns that do not appear at least once in an equality predicate in a query workload are pruned. Candidate column pairs not pruned are subsequently analyzed for spurious correlations, statistical correlations, and functional dependencies.

Correlation Detection Algorithm Overview

Shown in FIG. 2 is a correlation detection algorithm of CORDS. For simplicity, shown in FIG. 2 is an exemplary embodiment in which two input columns of interest both lie in some table R, are related via a trivial pairing rule, ∅_(R), and contain categorical, discrete-valued data. In another embodiment, columns of interest contain numerical data. In yet another embodiment in which pairing rule P is nontrivial, modifications to CORDS are straightforward; table R results from executing a join query on separate tables, as specified by P.

In CORDS shown in FIG. 2, |C|_(T) denotes the number of distinct values in column C of table T and |T| denotes the number of rows in table T. Similarly, |C₁, C₂|_(T) denotes the number of distinct values in the concatenation of columns C₁ and C₂ in table T. The jth most frequent value in a column C_(i) is denoted by V_(ij) and the corresponding frequency of the value is denoted by F_(ij). N_(i) denotes the number of frequent values for C_(i) stored in a database system catalog. Additionally, d_(i) denotes the number of distinct categories for C_(i) attribute values in a chi-squared test. Finally, G_(v) ⁻¹ denotes the inverse cumulative distribution function of a chi-squared random variable with v degrees of freedom. CORDS parameters ε₁ through ε₅ are small positive constants between zero and one and parameter p is a specified maximum allowable probability for a false-positive or false-negative chi-squared test result. Additionally, columns are labeled in a manner such that |C₁|_(R)≧|C₂|_(R).

Trivial Cases

In a first step of correlation detection, trivial cases are discovered by obtaining quantities |C_(i)|_(R) and |R| from a relational database system catalog. In step 200, the number of distinct values in each column C_(i) is compared to table cardinality |R|; if such a comparison satisfies the inequality, |C_(i)|_(R)≧(1−ε₁)|R|, then it is determined column C_(i) is a soft key. A soft key column is trivially statistically correlated to every other column in R because a value sampled from C_(i), determines, with high probability, the row and hence, an associated value in any other column. Therefore, CORDS eliminates an input column pair if at least one column is a soft key and subsequently terminates. In step 202, CORDS similarly eliminates an input column pair and terminates if at least one column is single-valued; for example, if |C_(i)|_(R)=1, then each column C_(j) with j≠i functionally determines C_(i) in a trivial manner.

Random Sampling

If CORDS has not discovered a trivial case for an input column pair, then data is sampled from an input column pair in preparation for further analyses. In step 204, rows of table R are randomly sampled to produce a reduced table S. In one embodiment, between 2,000 and 10,000 rows are sampled. In another embodiment, the following approximation is used to determine a number n of rows to sample from table R: $\begin{matrix} {n \approx \frac{\left\lbrack {{- 16}\quad\upsilon\quad{\log\left( {p\sqrt{2\quad\pi}} \right)}} \right\rbrack^{1/2} - {8\quad{\log\left( {p\sqrt{2\quad\pi}} \right)}}}{1.69\quad{\delta\left( {d - 1} \right)}\quad\upsilon^{- 0.071}}} & (2) \end{matrix}$ In (2), ν=(d₁−1)(d₂−2), d=min (d₁, d₂), and d₁ and d₂ are the number of categories C₁ and C₂, respectively, to be used in a chi-squared test for correlation, as determined from catalog statistics during value categorization described subsequently. Finally, δis a small constant and p is the probability of either: incorrectly declaring an input column pair to be independent when mean-square contingency, φ², satisfies φ²>δ; or incorrectly declaring an input column pair to be dependent when φ²<δ. Mean-square contingency is defined by $\begin{matrix} {\phi^{2} = {\frac{1}{d - 1}\quad{\sum\limits_{i = 1}^{d_{1}}{\sum\limits_{j = 1}^{d_{2}}{\frac{\left( {\pi_{ij} - {\pi_{i}.\pi._{j}}} \right)^{2}}{\pi_{i}.\pi._{j}}.}}}}} & (3) \end{matrix}$ In Eqn. (3), quantity π_(ij) is the fraction of (C₁, C₂) value pairs in table R of the form (x_(i), x₂) for which x₁ belongs to category i and x₂ belongs to category j, and quantities π_(i). and π._(j) denote marginal totals; ${{\pi_{i}.} = {{\sum\limits_{j}{\pi_{ij}\quad{and}\quad{\pi._{j}}}} = {\sum\limits_{i}\pi_{ij}}}},$ respectively. The case in which φ²=0 corresponds to complete “independence” of a joint frequency distribution: π_(ij)=π_(i).π._(j) for all values of i and j.

In one embodiment, a value for δ is chosen by considering a hypothetical set of |R| data pairs such that data pairs are generated according to a random mechanism for which two components of a pair are truly statistically independent, and subsequently choosing δ so that φ² exceeds δ with a small probability (e.g., less than 0.01). The value of δ is typically very small (e.g., for d=20, δ≈20/|R|, where |R| typically exceeds 1,000,000).

Soft Functional Dependency Detection and Identification

Continuing on to step 206, reduced table S is queried to obtain |C₁|S, |C₂|_(S) and |C₁, C₂|_(S). In step 208, CORDS asserts the existence of a soft FD, C₁

C₂, if |C₁|_(S)/|C₁, C₂|_(S) is close to 1, specifically, if |C₁|_(S)≧(1−ε₃)|C₁, C₂|_(S). CORDS also requires in step 208 that |S| is much greater than |C₁|_(S), specifically, that |C₁|_(S)≦ε₂|S|. Intuitively, if sample S is so small that most column-value pairs (x,y) are distinct, the likelihood is increased for the detection of a spurious FD.

The strength of a soft FD C₁

C₂ is defined as |C₁|_(R)/|C₁, C₂|_(R). The strength of a soft FD is less than or equal to 1, and a soft FD with strength equal to 1 coincides with a hard FD. CORDS estimates the strength of a soft FD by |C₁|_(S)/|C₁, C₂|_(S).

Skew Handling and Categorization for Chi-Squared Test

If CORDS does not assert the existence of a soft FD for an input column pair, then CORDS analyzes a chi-squared test for forms of correlation that are more general than soft FDs. To prepare data for a chi-square test, CORDS decomposes the domain of values for each column into a number of disjoint categories, and then creates a contingency table from reduced table S obtained from by sampling step 204. A contingency table is a two-dimensional array of n_(ij) values along with the marginal row (n_(i).) and column (n._(j)) totals; n_(ij) is interpreted as the number of (C₁, C₂) value pairs (x₁, x₂) in S such that x₁ belongs to category i and x₂ belongs to category j, respectively.

CORDS constructs the contingency table so as to ensure that each n_(ij) is sufficiently large. Specifically, in step 210, CORDS examines for each column the n-most-frequent-value statistics (recorded in a system catalog) to check whether the most frequently-occurring values for a column account for a majority of values, such that data distribution is noticeably skewed. If the data distribution is determined to be skewed in step 210 then subsequently, in step 212, CORDS filters out infrequent values from sampled data, so that the chi-square test is applied to frequent values. Otherwise, if data distribution is not identified as skewed in step 210, CORDS continues to step 214. After an initialization in step 214, CORDS constructs a contingency table in step 216. If data distribution for an input column has been identified as skewed in step 210, then frequently-occurring values determined from a consultation of a system catalog are used as categories in construction of a contingency table. Otherwise, CORDS bucketizes data values by hashing, in effect creating categories by dividing the domain of column values into equal size subsets. CORDS also uses a bucketization approach to categorize real-valued data, in which case categories correspond to disjoint sub-intervals of the real number line.

Sampling-Based Chi-Squared Test

In step 218|, CORDS declares columns C₁ and C₂ to be correlated if there are more than a given number of zeros in the contingency table constructed in step 216, wherein zeros persisting as categories despite hashing and bucketization are considered structural zeros. If there are less than a given number of zeros, then the chi-squared test is applied. Specifically, in step 220|, a chi-square statistic is computed according to the equation $\begin{matrix} {\chi^{2} = {\sum\limits_{i = 1}^{d_{1}}{\sum\limits_{j = 1}^{d_{2}}\frac{\left( {n_{ij} - {n_{i\quad\bullet}n_{\bullet\quad j}}} \right)^{2}}{n_{i\quad\bullet}n_{\bullet\quad j}}}}} & (4) \end{matrix}$ In step 222, an input column pair is identified as correlated if χ² exceeds a critical value given by t=G_(v) ⁻¹(1−p). Essentially, if mean-square contingency φ² is less than δ implying independence of input columns, then the probability that χ²>t is less than p. If φ² exceeds δ, implying a correlation between columns in an input pair, then the probability that χ²<t is less than p.

In an alternative embodiment of step 222, a quantity p*=1−G_(v)(χ²) is computed and an independence hypothesis is rejected if p* is less than a cutoff value p-value; a p-value being the probability of encountering a value of χ² at least as large as an actual value, given that chosen attributes are truly independent. Thus, a p-value is inversely proportional to the probability that input columns are correlated and a cut-off value for p-value is the maximum allowable probability of incorrectly asserting correlation in the presence of independence.

Dependency Graph—Displaying Results

Referring now to FIG. 3, exemplary CORDS output is displayed as a dependency graph in which node pairs represent column pairs and edges connecting node pairs correspond to correlation or soft FD relationships. Properties of edges, (e.g., cost, thickness, color) are used to indicate the strength of a soft FD relationship between columns in a pair as well as the degree of correlation between columns in a pair. For soft FDs, such a property is an increasing function of estimated strength and for degree of correlations, such a property is either of: a decreasing function of a statistical p-value or an increasing function of an estimated mean-square contingency, {circumflex over (φ)}², where {circumflex over (φ)}²=χ²/(n(d−1)), with χ² defined as in Eqn. (4), d=min(d₁, d₂) as before, and n equal to the number of rows in the reduced table S.

Query Optimization—Use of Column-Group Statistics and Recommendations

To estimate the selectivity of a conjunctive predicate p₁{circumflex over ( )}p₂ for two columns C₁ and C₂ from some specified table, where each p_(i) is an equality predicate of the form C_(i)=ν_(i), a query optimizer produces a selectivity estimate by estimating an initial selectivity of each p_(i) as S_(p) _(i) =1/|C_(i)|, where |C_(i)| is the number of distinct values in C_(i), and then obtaining a final selectivity estimate as S_(p) ₁ _({circumflex over ( )}p) ₂ =S_(p) ₁ ·S_(p) ₂ =1/|C₁|/·1/|C₂|.

The foregoing selectivity estimates for the individual predicates p₁ and p₂, assume that values in each column are uniformly distributed, and that C₁ and C₂ are independent. CORDS provides a query optimizer with a set of CG statistics to provide for underestimation of the true selectivity by orders of magnitude.

CORDS identifies a set of column pairs that are strongly correlated; for each such pair (C₁, C₂), a query optimizer collects a CG statistic |C₁, C₂|, the number of distinct combinations of values in the two columns. The optimizer then produces an improved selectivity estimate S′_(p) ₁ _({circumflex over ( )}p) ₂ =1/|C₁, C₂|. To create an improved estimate, an adjustment factor for S_(p) ₁ _({circumflex over ( )}p) ₂ , |C₁| |C₂|/|C₁, C₂|, is applied to a selectivity estimate made by a query optimizer. Such an adjustment factor is equal to 1 when input columns are truly independent and increases proportionally with the degree of correlation between columns in an input pair.

Referring now to automobile data in FIG. 4, a query having a selection predicate p₁{circumflex over ( )}p₂, where p₁=“Make=Honda” and p₂=“Model=Accord” is issued against ID column 400, “Make” column 402, and “Model” column 404. The true selectivity of this predicate is σ_(p) ₁ _({circumflex over ( )}p) ₂ =1/10. The naïve estimate is S_(p) ₁ _({circumflex over ( )}p) ₂ =1/|Make|·1/|Model|=1/7·1/8=1/56, which underestimates the true selectivity by a factor of 5.6, or about −82%. After applying an adjustment factor of |Make| |Model|/|Make, Model|=56/9, an adjusted selectivity estimate of S′_(p) ₁ _({circumflex over ( )}p) ₂ =1/9, is obtained.

In FIG. 5, an algorithm for recommending column group statistics is shown. A query optimizer collects a detailed set of CG statistics comprising not only distinct-value information, but also the frequencies for the k most frequent values, along with quantiles, when prompted by CORDS. In step 500, correlated column pairs are prioritized by either of: ascending order of p-value or descending order of estimated mean-square contingency; both ensure a higher priority assigned to column pairs that are more strongly correlated. Soft FDs are prioritized in a descending manner according to estimated strength in step 502. A tie-breaking rule prioritizes column pairs with respect to an adjustment factor in step 504; column pairs upon which CG statistics have the greatest impact on improving query optimizer selectivity estimates are given a higher priority. In another embodiment, an adjustment factor is used as a primary prioritization criterion rather than a tie-breaker. Lastly, in step 506, query optimizer stores recommended CG statistics for k₁ prioritized correlated column pairs and k₂ prioritized soft FDs.

CORDS advantageously exploit query workload information to limit the search space of possibly correlated column pairs; additionally, CORDS also exploits schema constraints and semantics provided by users. CORDS approach is also well-suited to integration with a QFS such as LEO. In contrast with prior art approaches, CORDS handles either numerical or categorical data.

Because CORDS identifies correlated columns pairs instead of producing detailed approximations as to a joint attribute frequency distribution for the pair, overhead is typically much lower than that of more elaborate techniques. Another advantage lies in the use of sampling to further reduce overhead relative to other methods, so thus making CORDS well-suited to real-world databases having thousands of tables and hundreds of columns per table. Lastly, CORDS provides benefits by efficient dealings with data that is continually changing, since re-checking column pairs for correlation is less expensive than updating a multivariate distribution synopsis of data values in a relational database.

Additionally, the present invention provides for an article of manufacture comprising computer readable program code contained within implementing one or more modules to detect correlations and soft functional dependencies between column pairs in one or more relational databases. Furthermore, the present invention includes a computer program code-based product, which is a storage medium having program code stored therein which can be used to instruct a computer to perform any of the methods associated with the present invention. The computer storage medium includes any of, but is not limited to, the following: CD-ROM, DVD, magnetic tape, optical disc, hard drive, floppy disk, ferroelectric memory, flash memory, ferromagnetic memory, optical storage, charge coupled devices, magnetic or optical cards, smart cards, EEPROM, EPROM, RAM, ROM, DRAM, SRAM, SDRAM, or any other appropriate static or dynamic memory or data storage devices.

Implemented in computer program code based products are software modules for:

-   -   (a) selecting column pairs from a relational database or         databases; (b) sampling value pairs from selected column         pairs; (c) identifying column pairs between which functional         dependencies exist; (d) preparing remaining column pairs for         test of statistical correlation; (e) testing correlation between         sampled value pairs in a prepared set of column pairs; (f)         graphically displaying results of discovery; (g) prioritizing         column pairs between which correlations or soft functional         dependencies exist; and (h) recommending prioritized column         pairs for use in query optimization.

CONCLUSION

A system and method has been shown in the above embodiments for effectively implementing data correlation detection. While various preferred embodiments have been shown and described, it will be understood that there is no intent to limit the invention by such disclosure, but rather, it is intended to cover all modifications falling within the spirit and scope of the invention, as defined in the appended claims. For example, the present invention should not be limited by software/program, computing environment, or specific computing hardware.

The above enhancements are implemented in various computing environments. For example, the present invention may be implemented on a conventional IBM PC or equivalent. All programming and data related thereto are stored in computer memory, static or dynamic, and may be retrieved by the user in any of: conventional computer storage, display (i.e., CRT) and/or hardcopy (i.e., printed) formats. The programming of the present invention may be implemented by one of skill in the art of database programming. 

1. An a priori method of identifying dependencies and discovering correlations between column pairs from one or more relational databases and applying said discoveries in query optimization; said method comprising: a. selecting column pairs from said relational database or databases; b. collecting a random sample of value pairs from said selected column pairs; c. identifying functionally dependent column pairs; said column pairs identified by detection of soft functional dependencies between value pairs in said collected sample; d. preparing a set of value pairs using system catalog statistics for said relational database or databases; said set comprised of value pairs in said collected sample for which soft functional dependencies were not detected; and e. discovering correlated column pairs by testing for, using said test statistic, correlations between said sampled value pairs in prepared set; and f. recommending to said query optimizer, said functionally dependent and correlated column pairs.
 2. An a priori method of discovering dependencies, as per claim 1, wherein said selection comprises: a. generating candidate column pairs from said relational database or databases; b. pruning said candidate column pairs with respect to a set of heuristic constraints; said candidate column pairs pruned simultaneously with said generation of candidate column pairs; and c. eliminating said candidate column pairs having trivial instances of correlation; said trivial instances identified by system catalog statistics for said relational database or databases.
 3. An a priori method of discovering dependencies, as per claim 1, wherein said soft functional dependency between value pairs in said collected sample is detected by a ratio of the cardinality of distinct sampled values in one of said column pair divided by the cardinality of distinct combinations of sampled values pairs from said column pair; said soft functional dependence indicated by said ratio being either of: greater than or equal to, a parameter value subtracted from one, if said collected sample is larger than the cardinality of distinct value pairs in said column pair.
 4. An a priori method of discovering dependencies, as per claim 1, wherein said soft functional dependency has strength corresponding to a ratio of the cardinality of distinct values in one of said column pair divided by the cardinality of distinct combinations of value pairs from said column pair.
 5. An a priori method of discovering dependencies, as per claim 1, wherein said preparation comprises: a. obtaining frequently-occurring values from said system catalog statistics; b. if said obtained frequently-occurring values account for a proportion of said sampled values such that a statistical distribution of said sampled values is skewed, filtering infrequently occurring sampled values from said sampled column pairs, else, bucketizing sampled values by hashing said sampled values into equal size subset buckets; and c. creating a number of disjoint categories equal to the number of either of: said buckets or said distinct, frequently-occurring sample values; said categories computed for said test statistic; and d. building a contingency table for said test statistic; said contingency table comprising values from said column pairs.
 6. An a priori method of discovering dependencies, as per claim 2, wherein said heuristic constraints are based on at least one of: data types, statistical properties of said candidate column pairs, schema information, or query workload information.
 7. An a priori method of discovering dependencies, as per claim 2, wherein a ratio of the cardinality of distinct values in one of said column pair divided by the cardinality of distinct values in said relational database or databases indicates the existence of said trivial instance of correlation.
 8. An a priori method of discovering dependencies, as per claim 5, wherein said test statistic is a chi-squared test.
 9. A method of detecting correlation and functional dependence, as per claim 5, wherein correlation between said column pairs is detected on the basis of structural zeros in said contingency table.
 10. A method of detecting correlation and functional dependence, as per claim 6, wherein result of said chi-squared test determines degree of correlation between said column pairs.
 11. An a priori method of discovering dependencies, as per claim 7, wherein said trivial instance of correlation indicates a soft key if said ratio for at least one of said columns in said column pair is either of: greater than or equal to, a parameter value subtracted from one.
 12. An a priori method of discovering dependencies, as per claim 7, wherein said trivial instance of correlation indicates a trivial column if said ratio for at least one of said columns in said column pair is equal to one.
 13. A method of detecting correlation and functional dependence, as per claim 8, wherein sampling error in said chi-squared test is adjusted by statistical sample variance of said sample values.
 14. A system defining a dependency graph, comprising: at least two nodes representing at least two columns from one or more relational databases and at least one edge connecting said nodes; said edge representing either one of: a statistical correlation or a soft functional dependency between said represented columns.
 15. A system for defining a dependency graph, as per claim 14, wherein properties of said edges are proportionally weighted by at least one of: probability value, strength, or adjustment factor.
 16. A system for defining a dependency graph, as per claim 15, wherein said property is either of: a logical or a physical, property.
 17. A system for defining a dependency graph, as per claim 15, wherein said adjustment factor is the ratio of the cardinality of distinct values of a first column from said column pair multiplied by the cardinality of distinct values of a second column from said column pair, divided by the number of distinct combinations of value pairs from said column pair.
 18. A method for prioritizing functional dependencies and correlations between column pairs in one or more relational databases for referral to a query optimizer, comprising: a. sorting said correlated column pairs discoveries in ascending order of degree of correlation; b. sorting said functionally dependant columns in descending order of estimated strength; c. breaking ties between column pairs by sorting said pairs in descending order of an adjustment factor; said ties occurring between at least one of: pairs of functionally dependent columns having the same estimated strength and pairs of correlated columns having the same degree of correlations; and d. recommending a first number of said sorted correlated column pairs and a second number of said functionally dependent column pairs to said query optimizer.
 19. A method for prioritizing functional dependencies and correlations, as per claim 18, wherein said adjustment factor is computed by a ratio of the cardinality of distinct values of a first column in said column pair multiplied by the cardinality of distinct values of a second column in said column pair, divided by the number of distinct combinations of value pairs from said column pair.
 20. A method for prioritizing soft functional dependencies, as per claim 18, wherein said query optimizer tracks statistics for said recommended column pairs; said statistics either generated by or recommended to, said query optimizer.
 21. A article of manufacture comprising computer usable medium having computer readable program code embodied therein which, implements an a priori identification of dependencies and discovery of correlations between column pairs from one or more relational databases and applying said discoveries in query optimization, said medium comprising computer readable program code for: a. selecting column pairs from said relational database or databases; b. collecting a random sample of value pairs from said selected column pairs; c. identifying functionally dependent column pairs; said column pairs identified by detection of soft functional dependencies between value pairs in said collected sample; d. preparing a set of value pairs using system catalog statistics for said relational database or databases; said set comprised of value pairs in said collected sample for which soft functional dependencies were not detected; e. discovering correlated column pairs by testing for, using said test statistic, correlations between said sampled value pairs in prepared set; and f. recommending to said query optimizer, said functionally dependent and correlated column pairs.
 22. A article of manufacture comprising computer usable medium having computer readable program code embodied therein which implements a dependency graph, said medium comprising computer readable program code for: representing at least two columns from one or more relational databases by at least two nodes and representing a connection between said nodes by at least one edge; said edge representing either one of: a correlation or a functional dependency between said represented columns.
 23. A article of manufacture comprising computer usable medium having computer readable program code embodied therein which prioritizes functional dependencies and correlations between column pairs in one or more relational databases for referral to a query optimizer, said medium comprising computer readable program code for: a. sorting said correlated column pairs discoveries in ascending order of degree of correlation; b. sorting said functionally dependant columns in descending order of estimated strength; c. breaking ties between column pairs by sorting said pairs in descending order of an adjustment factor; said ties occurring between at least one of: pairs of functionally dependent columns having the same estimated strength and pairs of correlated columns having the same degree of correlations; and d. recommending a first number of said sorted correlated column pairs and a second number of said functionally dependent column pairs to said query optimizer. 